DataForSEO v3 Migration Guide
Version three is designed for improving, speeding up and simplifying the general experience of working with our APIs. We have incorporated a number of quality enhancements that allow scaling up your operations, while the cost for API requests was decreased.
Migrating to the new version takes four simple but essential steps:
1. Log into the new dashboard
We have created a new stand-alone account dashboard for version three. You will notice that there are two options for logging in on our website. When you click on “Login”, choose DataForSEO API v3 from the dropdown menu to get into the new version’s dashboard.
2. Upgrade your examples
Same as we had it in the previous version, v3 runs on the REST technology and HTTP protocol, so you can apply our APIs to almost any programming language. We have prepared new examples for PHP, Python, and C#. You can download the necessary examples from the Introduction page of v3 and import them into your library.
3. Upgrade your code
As you start working with the new version, you will quickly find out this is not an incremental upgrade and it will take some effort to implement it. The good news, however, is that we’ve incorporated a number of new features and improved the overall usability of the API from the developer’s standpoint.
Before you start planning the migration, we recommend that you take some time to understand the difference between the versions. You can find a detailed explanation of changes in our blog.
4. Test and iterate
When you log into your new account for the first time, you will receive $1 for testing DataForSEO v3.
You can also use the free Sandbox feature to facilitate the migration process.
Once you are prepared to switch to the new version, you might have some funds remaining on your account balance. We have thought of this beforehand, and we want to reassure you that the migration will not drag any money loss. Drop a line to our support team if you would like to transfer the funds from v2 to your new v3 account balance.
Key improvements for a developer
|Standardized error/status codes and messages||read more
|Version 3 has a new, standardized set of error and status codes.|
|Streamlined URL structure of API calls||read more||URLs of the API endpoints now reflect its core parameters and functions.|
|Simple task identifiers||read more||All the parameters that you specified in the POST request are now reflected in the
|New pricing model||read more
|We reduced the prices and tied them to the US dollar.|
|Retrieving website rankings with SERP API||SERP API||You can get website rankings by filtering out relevant SERP results
|SERP functions in the GET request||SERP API||Your account will be charged for POST requests only.
By sending GET requests to Organic, Advanced and HTML endpoints,
you will get all three formats of the requested SERP at no additional cost
|New search engine types||SERP API||Google Organic/Maps/News/Images;
Bing Organic/Local Pack;
|Device & OS||SERP API||
|Location coordinates||SERP API, Keywords Data API||You can get data for a particular location by specifying its GPS coordinates
|Bulk-only search volume||Keywords Data API||You can get search volume for up to 700 keywords,
the price for one or 700 keywords will be the same
Core v2/v3 parallels
Deprecated v2 endpoints
DataForSEO API v3 has parallels for most of the v2 functionality. There are, however, a few functions that have been deprecated. The main reason for this is that the majority of them were not popular among users. When planning your migration, you should either remove the following references from your code or implement the workarounds described here.
Deprecated ‘List of Search Engines’ endpoints for SERP API
SERP API v3 determines the search engine domain automatically according to the location and language parameters you set in the POST request.
Search Volume for Keyword
In v3 you can get search volume for up to 700 keywords using Google Search Volume endpoints
Don’t hesitate to contact our support team if you have any questions or need assistance with the migration process.